Summary

• Fixes #947: the published loro-crdt sourcemaps emit sources: ["../../index.ts"], which — resolved from node_modules/loro-crdt/<target>/index.js.map — escapes the package, so Vite/Vitest log: "Sourcemap for ... points to a source file outside its package: 'node_modules/index.ts'".
• Root cause: @rollup/plugin-typescript hands rollup a map whose sources are relative to TS's intended JS output, but rollup resolves them against the .ts source directory, leaving an extra .. segment in the published map. Separately, sourcesContent was null because the plugin only auto-enables inlineSources when sourceMap is unset — but our tsconfig sets inlineSourceMap: true, which the plugin rewrites to sourceMap: true while leaving inlineSources off.
• Fix in crates/loro-wasm/rollup.config.mjs:
  • Add output.sourcemapPathTransform that detects sources resolving outside the package and rewrites them to the real file inside the package (one less ..).
  • Set compilerOptions.inlineSources: true on the TS plugin so sourcesContent is populated.

After the fix, all four targets (nodejs, bundler, web, browser) emit sources: ["../index.ts"] with 12 788 chars of sourcesContent. Resolved from a published node_modules/loro-crdt/<target>/index.js.map, that lands on node_modules/loro-crdt/index.ts — inside the package — silencing the Vite warning.

Test plan

• Rebuild rollup outputs and verify each */index.js.map's sources resolves inside the package
• Verify sourcesContent is populated (no null)
• After this PR's release, install loro-crdt in a Vite/Vitest project and confirm the warning is gone

🤖 Generated with Claude Code